-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow configuring cancelling synthetic click behavior #5533
Allow configuring cancelling synthetic click behavior #5533
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am okay for this. Let's see what the others say before merging.
296752a
to
00d4cdf
Compare
@TimvdLippe Thanks! I also created the 2.x version: #5536 |
@sorvell @kevinpschaaf @azakus could you take a look at this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This config enabled is really for legacy mobile browser support, this is no longer needed, so lets disable it. This also fixes file uploads in mobiles. See Polymer/polymer#5533 Change-Id: I2144b848a892e6b908dcc153fed42b9223c06272
Fixes #5289
The polymer gestures module cancels synthetic mouse clicks fired by old mobile browsers. This is no longer necessary (see https://developers.google.com/web/updates/2013/12/300ms-tap-delay-gone-away).
The cancellation detection incorrectly cancels programmatic clicks from javascript directly following a touch action. I added a failing test which demonstrates this behavior. If you run the test in chrome with device simulation enabled, the test would fail if the synthetic click events option is set to true.
This PR adds an option to allow configuring this behavior, leaving the default behavior intact to avoid breaking changes.
If this change is accepted, could we backport this to the Polymer 2 branch as well?